The generation of PROC OLAP code from within SAS OLAP Cube Studio or SAS Data Integration Studio might cause the client application to hang. This will occur when metadata components are missing from the table registrations.

When a cube is created from star schema input, two items are added to the column registrations within the tables. The first is a ForeignKey registration and it is associated with a PartnerUniqueKey. If either component is later deleted, the generation of the PROC OLAP will fail and the client will become unresponsive.

It is possible to correct these fields so that the code can be generated. The following instructions can be used to accomplish this, or you can use the data step code included on the Full Code tab. Before performing any modifications, we strongly recommend that you back up the SAS^® Metadata Server and your data.

1. Open SAS Management Console.
2. Select Tools ► Metadata Utility.
3. On the Get Metadata Objects tab, specify the following fields and then click Execute.
   • Type: PhysicalTable
   • Flags: OMI_GET_METADATA
4. Locate your fact table from the list of displayed tables.
5. Copy and paste the entire fact table definition into the Input XML field. For example:

   <PhysicalTable Id="A5DZ22JM.BK0003VU" Name="ORDER_FACT" Desc=""/>

6. Click the Get Metadata tab and select the OMI_ALL flag before clicking Execute.
7. Copy the list of foreign keys from the Output XML field to a text editor. For example:

   <ForeignKey Id="A5DZ22JM.BP0003V1" Name="FactTable_ForeignKey" Desc=""/>
   <ForeignKey Id="A5DZ22JM.BP0003V2" Name="FactTable_ForeignKey" Desc=""/>
   <ForeignKey Id="A5DZ22JM.BP0003V3" Name="FactTable_ForeignKey" Desc=""/>
   <ForeignKey Id="A5DZ22JM.BP0003V4" Name="FactTable_ForeignKey" Desc=""/>

8. Perform the following steps for each item in your ForeignKey list:
   1. Copy the entries one at a time into the Input XML field on the Get Metadata tab. Click Execute.
   2. Examine each ForeignKey to determine whether a PartnerUniqueKey association exists. Delete any ForeignKey that does not have an associated PartnerUniqueKey. To delete, click the Delete Metadata tab. Click Execute. The object listed in the Input XML field will be deleted.

Operating System and Release Information

Before modifying any metadata, back up your SAS Metadata Server.

You must update the options at the top of the code before submitting.

options 
metaserver="your server"
metaport=8561
metaprotocol=bridge
metauser="Your User"
metapass="Your Password"
metarepository="Foundation";

data _null_;
  length uri_fk $256;
  length uri_pk $256;
  length status $256;
  nobj=0;
  n=1;
  nobj=metadata_getnobj("omsobj:ForeignKey?@Id contains '.'",n,uri_fk);
  do i = 1 to nobj;
    nobj=metadata_getnobj("omsobj:ForeignKey?@Id contains '.'",i,uri_fk);
    nasn=metadata_getnasn(uri_fk, "PartnerUniqueKey", n, uri_pk);
    if nasn = -4 then do;
      status =  catt(uri_fk,' should be deleted');
      deletion = METADATA_DELOBJ(uri_fk);
      select (deletion);
        when (0)  status = catt(uri_fk, ' was successfully deleted');
        when (-1) status = 'Unable to connect to the metadata server';
        when (-2) status = 'The deletion was unsuccessful. See the SAS log for details';
        when (-3) status = 'No objects match the given URI';
        otherwise;
      end;
    end; 
    else status = catt(uri_fk,' should not be deleted');
    put status;
  end;
run;